Fix dtc_output read when interrupted by EINTR #1801
Conversation
The read() call may be interrupted by a signal, resulting in an EINTR error. In this case, read() will return -1 and set errno to EINTR. This is a common issue when dealing with I/O in a multi-process environment. Check the error code returned by errno. If it is EINTR, we can safely retry the read().
There was a problem hiding this comment.
There are myriad I/O calls within Spike. I'm not yet convinced we need to solve this problem--can't we just be OK with it being undefined to send signals to Spike?--but if we do solve it, we should solve it systematically rather than providing a point solution to this one read call.
The reason I write this fix was that when running spike using lldb debugger I was always getting -1 from the read, preventing the model to actually run. |
|
Yeah, probably best to file an issue for the time being. |
2 participants
The read() call may be interrupted by a signal, resulting in an EINTR error. In this case, read() will return -1 and set errno to EINTR. This is a common issue when dealing with I/O in a multi-process environment.
Check the error code returned by errno.
If it is EINTR, we can safely retry the read().